Scroll Bridge.

The Scroll Bridge locks your deposit in an Ethereum contract and mints the matching asset on Scroll, where it behaves exactly as it did on mainnet because the zkEVM is bytecode-equivalent. Nothing about the asset changes shape in transit — the same ERC-20 you held on Ethereum arrives on Scroll with the same decimals, the same symbol, and the same approval model your wallet already understands. A withdrawal runs the same logic in reverse: the asset is burned or released on Scroll and the matching amount unlocks on Ethereum once the exit is proven. At no point does a third party hold your funds; the contracts do the accounting and you hold the keys.

Why bytecode equivalence matters

Scroll does not reimplement the EVM in a modified form — it runs the same bytecode Ethereum runs, down to the opcode level, as the official documentation lays out. That means contracts, compilers and developer tooling built for Ethereum deploy on Scroll without rewrites, and it means a token bridged through the Scroll Bridge keeps behaving like the token you already know rather than a wrapped approximation of it.

What you can bring across

ETH and major stablecoins such as USDC and USDT are the common deposits, and the same canonical route carries most ERC-20 tokens Scroll supports. Whatever you send keeps its identity on the other side, and the same path takes it back to Ethereum whenever you want to exit.

Every batch of Scroll transactions is proven to Ethereum with a zero-knowledge validity proof, so the base chain mathematically verifies the new state rather than trusting an operator to report it honestly. There is no challenge period during which someone has to notice and dispute a bad state — the proof itself is the check, and Ethereum either accepts it or it fails. For you as a user of the Scroll Bridge, that means a withdrawal does not depend on a watchtower staying online or a long fraud-proof window elapsing; it clears once the proof covering your transaction is verified and finalized on Ethereum.

A Scroll Bridge deposit costs Ethereum gas to run the locking transaction, plus a small protocol fee; once your assets are on Scroll, further activity costs a fraction of mainnet because execution happens off the most expensive chain while validity proofs keep it provably correct. Timing is not symmetric. Deposits credit within minutes of your Ethereum transaction confirming, but a withdrawal has to wait for the batch containing it to be proven and that proof finalized on Ethereum, which takes longer than the deposit side. The table below sets out what to expect on each leg of a bridge transfer.

Direction	What you pay	Typical time
Deposit to Scroll	Ethereum gas + small protocol fee	Minutes after confirmations
Activity on Scroll	ETH gas (low cost)	Seconds
Withdrawal to Ethereum	Scroll gas, then Ethereum gas to finalize	Until the next proof is finalized

Judge a route by the net amount

Compare any bridge route by the net amount received after gas and fees, not the headline rate. The Ethereum gas on a deposit is a fixed cost regardless of size, so bridging a tiny amount wastes a disproportionate share of it — batching a larger transfer spreads that fixed cost across more value.

Once your assets land on Scroll, they plug directly into its EVM apps — decentralized exchanges, lending markets and liquidity pools — through the same MetaMask flow and the same Ethereum-style addresses you already use, because bytecode equivalence means nothing about the developer experience had to change. Keep a small ETH balance on Scroll to cover gas for your first few transactions there; it is the same ETH you bridged, not a separate network token, so there is nothing new to acquire. When you are ready to bring native ETH or a token back to mainnet, withdraw through the same canonical Scroll Bridge route rather than an unfamiliar third-party path.

The flow is identical every time you use it, which is what makes the process predictable once you have run it once.

• Connect your self-custody wallet and choose Ethereum as the source and Scroll as the destination.
• Enter the amount; the interface shows the fee and the amount that will arrive.
• Approve the token if it is an ERC-20, then sign the deposit transaction and pay Ethereum gas.
• Wait for Ethereum confirmations — your balance appears on Scroll a few minutes later.
• To exit, start a withdrawal on Scroll and wait for the covering validity proof to finalize, then claim on Ethereum.

Why withdrawals take longer than deposits

A deposit only needs Ethereum to confirm your transaction, which happens in minutes. A withdrawal has to wait for the batch holding it to be wrapped in a zero-knowledge validity proof and for that proof to be verified and finalized on Ethereum — a process that protects every user's exit, including yours, and is why the exit side of the Scroll Bridge runs on proof time rather than confirmation time.

A canonical Scroll Bridge never takes custody of your assets — your keys stay in your own wallet from the first signature to the last — so the risks that remain are the ones you control at the moment you sign. Confirm the destination contract address on a block explorer, check the amount you will receive against the amount you sent, and read the approval you are granting before confirming it.

Approvals and allowances

Grant a limited approval rather than an unlimited one whenever the interface offers the choice, so a contract can only ever move the amount you intend, and revoke old allowances on tokens you no longer bridge. Fewer standing approvals means a smaller surface for any single exploit to reach.

The one rule that never changes

No bridge, wallet or support contact ever needs your seed phrase. Anyone who asks for it, in a chat window or a form, is attempting fraud. The real Scroll Bridge only ever asks you to sign a transaction you can read in your own wallet — it never asks you to type or paste your recovery words anywhere.

You can reach Scroll through the canonical Scroll Bridge or through an independent liquidity bridge. The canonical route mints the official representation of your asset through the proven contract pair, and it is the reference path for large transfers or anything you intend to hold on Scroll for a while. A third-party bridge can shorten a withdrawal because it fronts liquidity instead of waiting for proof finalization, but it adds its own fee on top and its own trust assumptions on top of Scroll's. For most transfers the simple rule holds: use the canonical route unless you specifically need a faster exit and have checked the third party's track record on an independent risk tracker and the net amount it actually quotes you.